Skip to content

ci(tooling): verify scripts/check-tools.sh runs successfully in CI - #519

Open
maisamariwanta4-bit wants to merge 1 commit into
WHEELBACK:mainfrom
maisamariwanta4-bit:ci/check-tools-script-verification
Open

ci(tooling): verify scripts/check-tools.sh runs successfully in CI#519
maisamariwanta4-bit wants to merge 1 commit into
WHEELBACK:mainfrom
maisamariwanta4-bit:ci/check-tools-script-verification

Conversation

@maisamariwanta4-bit

Copy link
Copy Markdown

Summary

Add CI verification that scripts/check-tools.sh runs successfully to ensure the environment verification script itself doesn't regress.

Description

The check-tools.sh script verifies that the development environment has the correct versions of Rust, stellar-cli, and the wasm32-unknown-unknown target installed. Previously, this script was only run manually by contributors and never exercised by CI, meaning any regressions in the script itself (like from version pin bumps) wouldn't be caught automatically.

This PR adds a new step to the init-smoke-test workflow that runs check-tools.sh after installing the pinned toolchain versions, confirming it correctly validates the CI environment.

Changes

  • Add new step to that runs scripts/check-tools.sh
  • Update workflow trigger paths to include scripts/check-tools.sh so the workflow runs whenever the script changes
  • Step runs after Rust/Stellar CLI installation but before running other tests

Testing

The check-tools.sh script will verify:

  • Rust version is 1.95.0
  • wasm32-unknown-unknown target is installed
  • stellar-cli version is 22.8.2

All of these are installed by preceding CI steps, so the verification should pass.

closes #433

Add a step to the init-smoke-test workflow that runs scripts/check-tools.sh to
verify the CI environment's toolchain (Rust 1.95.0 and stellar-cli 22.8.2) and
wasm32-unknown-unknown target are correctly installed and accessible.

Also update the workflow trigger paths to include scripts/check-tools.sh so the
workflow runs whenever the script is modified, catching any regressions in the
verification script itself before they affect contributor experience.
@drips-wave

drips-wave Bot commented Aug 29, 2026

Copy link
Copy Markdown

@maisamariwanta4-bit Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add a CI job that verifies a fresh clone + scripts/init-contracts.sh + scripts/check-tools.sh succeeds end-to-end

1 participant